System and method for web-based real time communication with contact centers

ABSTRACT

A method for connecting a website user to a contact center agent includes: monitoring user interaction associated with the website user; receiving a call request via the website; identifying an agent or an interactive voice response based on the monitored user interaction; and establishing a communication channel supported by a web browser between the website user and the identified agent or the interactive voice response.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/669,384, filed on Nov. 5, 2012, now U.S. Pat. No. 9,112,975, thedisclosure of which is hereby incorporated by reference in its entirety.

FIELD

Embodiments of the present invention are directed to systems and methodsfor operating contact centers, and more particularly, to systems andmethods for communicating with users using web browser basedcommunication channels.

BACKGROUND

In the field of customer communications and services, an organizationsuch as a retail company, a service company, or a non-profitorganization may operate a website for providing information tocustomers and clients and/or for providing an entry point ofcommunication with a contact center. In addition to the website, theorganization may also operate a contact center (e.g. customer service orsales contact center) staffed by people who communicate with customersvia a telephone or other audio/visual communication channel, interactivetext chat systems, short message service (SMS), social, media,cobrowsing, email letters, fax, etc.

Generally, visitors to an organization's website are presented withinformation and opportunities for contacting representatives of theorganization at the contact centers. These opportunities are typicallypresented as toll-free numbers (e.g., “1-800” numbers) for voicecommunications and/or chat boxes or windows integrated into a web pagefor real-time text-based communications. In some circumstances, a useris given the opportunity to fill out a form to indicate what they wouldlike to speak about and to provide their telephone number for arepresentative of the organization to call the user (either immediatelyor at a designated time) using the public switched telephone network(PSTN).

However, operating toll-free numbers and maintaining a sufficientlylarge number of PSTN lines can often be expensive for organizations. Inaddition, voice communication over a PSTN connection is generallylimited to audio and is substantially separate from and independent ofthe particular browser session currently being used by the caller.

Many organizations often use Data Network Telephony (DNT) or“computer-simulated telephony” to provide increased flexibility inhandling higher numbers of calls through the use of shared,connectionless data networks such as the Internet. In such DNT systems,high loads can be handled by, for example, gracefully degrading callquality during peak usage through Quality of Service (QoS) mechanisms.For example, a DNT system may be implemented in part using telephonesand gateways based on a Session initiation Protocol (SIP), as described,in part, in Internet Engineering Task Force (IETF) Request for Comments(RFC) 2543, 3261, and 3262.

Whether the contact centers use PSTN lines, DNT connections, other typesof telephonic communication systems, or combinations thereof, thecontact centers typically include some system for routing incoming callsto the appropriate parties. Such a system may include an interactivevoice response (IVR) system. The call can be connected to an IVR eitherbefore reaching the contact center switch, such as at the servicecontrol point (SCP) level or after reaching the contact center switch,such as through contact center routing means. During an IVR interaction,a voice application (or a chain of voice applications) is played for thecaller and the caller interacts with menu options that are played by thevoice application (e.g., “For new sales, press 1. For product support,press 2.”). Other IVR systems may also or alternatively provide voicerecognition systems (e.g., “Which flight would you like to know thestatus of? You can say the flight number or enter it on your keypad.”).Interaction with such enunciated voice menus may often be difficult.This may be due in part to confusion because of the recitation of manyoptions presented serially to the caller through the voice interface.Often a caller replays the menu and listens to the available optionsmultiple times before selecting an option. This creates delay in thesystem that could lead to delays in call processing and to reductions incall processing efficiency, and may sometimes result in callersabandoning calls due to frustration.

Accordingly, what is desired are economical systems and methods forcustomers to communicate with agents at contact centers and systems andmethods for determining user intentions for routing calls to particularagents.

SUMMARY

According to one embodiment of the present invention, a method forconnecting a website user to a contact center agent includes: monitoringuser interaction associated with the website user; receiving a callrequest via the website; identifying an agent or an interactive voiceresponse based on the monitored user interaction; and establishing acommunication channel supported by a web browser between the websiteuser and the identified agent or the interactive voice response.

The monitored user interaction may be associated with a sessionidentifier.

The establishing the communication channel may include identifying auser session using the session identifier.

The communication channel may include a WebRTC call leg.

The communication channel may include a SIP call leg between the agentand the user.

The communication channel may include a PSTN call leg between the agentand the user.

The communication channel may include a WebRTC call leg between theagent and the user.

The communication channel may include an audio channel.

The communication channel may include a video channel.

According to another embodiment of the present invention, a system forproviding connections with a contact center includes: a WebRTC-SIPgateway configured to receive a plurality of requests for connectionsbetween a session of a user on a website and the contact center; arouting server configured to route the requests for connections to aplurality of customer service representatives of the contact center; anda call server for establishing calls via the WebRTC-SIP gateway betweenthe user and a customer service representative of the contact center.

The routing server may be configured to route a request to a customerservice representative of the customer services representatives via thecall server.

The user on the website may be associated with a session identifier.

The system may further include a monitoring server configured to monitoruser interaction associated with the user of the website, wherein therouting server is configured to route the request to a customer servicerepresentative in accordance with the monitored user interaction, andwherein the call server is configured to establish the call byidentifying the user using the session identifier.

The call server may include a SIP server.

The WebRTC-SIP gateway may be farther configured to establish aWebRTC-to-SIP connection.

The WebRTC-SIP gateway may be further configured to establish aWebRTC-to-WebRTC connection.

The WebRTC-SIP gateway may be further configured to establish aSIP-to-SIP connection.

The calls may include an audio channel.

The calls may include a video channel.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, together with the specification, illustrateexemplary embodiments of the present invention, and, together with thedescription, serve to explain the principles of the present invention.

FIG. 1 is a block diagram of a system for web browser-basedcommunication between users and customer contact centers according toone exemplary embodiment of the present invention.

FIGS. 2A and 2B are flowcharts of a process for connecting a webapplication user to a contact center agent according to one exemplaryembodiment of the present invention.

FIG. 3 is a flowchart of a process for identifying the appropriate agentfor routing the call according to one exemplary embodiment of thepresent invention.

FIG. 4 is a flow diagram illustrating a process for establishing anout-of-band channel according to one exemplary embodiment of the presentinvention.

FIG. 5A is a schematic diagram of a browser window on a customerend-user device according to one exemplary embodiment of the presentinvention.

FIG. 5B is a schematic diagram of a browser window with a pop-up windowdisplaying a real-time video call with an agent according to oneexemplary embodiment of the present invention.

FIGS. 6A and 6B are schematic diagrams of browser windows with pop-upwindows displaying requests for additional information from a customer,according to one exemplary embodiment of the present invention.

FIG. 7 is a schematic diagram of a browser window displayed by theend-user device of a customer engaged in a communication session with acustomer service representative and with a plurality of out-of-bandchannels according to one exemplary embodiment of the present invention.

DETAILED DESCRIPTION

In the following detailed description, only certain exemplaryembodiments of the present invention are shown and described, by way ofillustration. As those skilled in the art would recognize, the inventionmay be embodied in many different forms and should not be construed asbeing limited to the embodiments set forth herein. Like referencenumerals designate like elements throughout the specification.

Exemplary embodiments of the present invention are directed to a systemand method for establishing one or more communications channels withvisitors to a website and a customer service representative (alsoreferred to as an agent) using a web browser-based communication system.Such a system may be, for example, a Web real-time communication(WebRTC) system. WebRTC, which is also known as RTCWeb, enables a webbrowser to provide real-time communications (RTC) capabilities viaJavaScript application programming interfaces (APIs) without requiring auser to actively download and install additional software andessentially makes bidirectional media processing and media codingtechnologies available in every browser. WebRTC technology puts a mediaengine into a browser or other elements of client devices. The mediaengine is the technology that manages microphones, cameras, and speakersand gets audio and video onto and off the internet. Thus, a visitor tothe website desiring to speak to an agent simply actuates a call buttondisplayed on the website, and a voice and/or video connection is formedbetween the visitor and an agent over, e.g. the Internet, withoutrequiring that the visitor install any standalone applications orbrowser plug-in. The visitor also need not leave his/her current webbrowsing session and initiate a separate call session for engaging in aweb browser based voice communication with the agent.

In one exemplary embodiment of the present invention, the user'sactivity on the website is monitored and information derived frommonitoring the activity is used to determine whether or not to offer alive agent (e.g., a live communication with a customer servicerepresentative). If offered a live contact, the user may choose to speakto an agent (e.g., via text chat, telephone, WebRTC, or anotherteleconferencing service). The organization may route the user to anagent based on the user's prior activity on the website. For example, afirst user looking primarily at a particular category of products (e.g.,laptops) available for sale on the website would be directed to a salesagent with specialized knowledge of that category. As another example, asecond user browsing portions of the website associated withtroubleshooting problems associated with a particular product would berouted to a customer support agent such as a technical support agent. Asa third example, a customer browsing a Spanish or Chinese version of thewebsite may be routed to a Spanish or Chinese speaking customer servicerepresentative, respectively.

According to one exemplary embodiment of the present invention, a usermay utilize an out-of-band (OOB) or supplemental channel for providingand receiving additional information to and from agents and end usersbefore, during, and/or after a call, e.g., by telephone, WebRTC, orother voice over IP communication channel. In some embodiments, the OOBchannel is dynamically offered by the contact center through the webserver such that the decision to offer the OOB channel is made by thecontact center and the user is provided the option to accept or ignorethis channel. According to one exemplary embodiment, the OOB orsupplemental channel may include any communication channel which islogically linked to the real time communication channel used for videoand/or audio conversation between agents and end users but may beseparate from the real time communication channel with respect to theprotocol and transmission. For example, the display of the OOB channeldata could be either separated from or grouped with the real timecommunication display. According to one embodiment of the presentinvention, the OOB channel is used to display of pictures or movies, ora graphical presentation of an IVR selection menu. In some embodiments,the additional information may be received via the OOB channel afterestablishing a call but before connecting the call with an agent. Inother embodiments, when the additional information is received via theOOB channel before establishing a call, it may be used to assist inrouting the user to an appropriate agent.

In some embodiments, when the customer initiates a call using WebRTC,the contact center actively initiates or offers an OOB or supplementalchannel to the user to, for example, show the graphical presentation ofthe IVR menu and for the agent to push content to the user. For example,according to one exemplary embodiment of the invention, the OOB channelmay also be a text chat window where the additional information isexchanged between agents and end users via text chat. The OOB channelmay also be, for example, a medium for sharing images (e.g.,screenshots), recorded videos, documents (e.g., tutorials and orderforms), links to other web pages, and/or a medium for sharing screens(e.g., using remote desktop technology such as remote framebuffer,Microsoft® Remote Desktop Services®, and other similar technologies).The OOB channel may also provide a backup communication channel ifWebRTC is unreliable due to an unstable a poor Internet connection.Furthermore, the OOB channel can provide data without being restrictedby quality of service (QoS) requirements that may be in place for datathat is transferred in an in-band channel, such as a WebRTC channel.

In some exemplary embodiments, in addition or in lieu of any informationprovided via the OOB channel, the agents may also be with suppliedinformation regarding the user's browsing history on the organization'swebsite and, if available, the users' responses to web browser-basedforms, in order to provide the agent with a better understanding of theissues the user may be facing.

FIG. 1 is a block diagram of a system for web browser-basedcommunication system between web users and customer contact centersaccording to one exemplary embodiment of the present invention. A useror customer may use a web browser 11 installed in an end-user device 12to access a web server 120 via a data communications network 20 such as,for example, the Internet. The end-user device 12 may be a standarddesktop or portable computer, tablet, smartphone, television, gameconsole, or any other device capable of running a web browser as isconventional in the art. The web server 120 may be configured to host aweb application or website 122 that provides information such asfeatures and specifications of products or services available from anorganization and/or technical support for those products or services.The web server 120 may also be configured to drive the WebRTC sessionsand the OOB communication channel to the web browser 11 by supplying,for example, JavaScript code.

According to one exemplary embodiment, a contact center 10 may beoperated by the organization or by another entity. The contact center 10may, according to one example, include a WebRTC/call server or gateway110 for receiving incoming requests to establish WebRTC calls, and arouting server 160 for routing incoming requests from the WebRTC/callserver 110 to appropriate agents at the contact center. According to oneembodiment, the WebRTC/call server 110 is configured to receive andestablish WebRTC sessions and acts as a gateway between WebRTC and SIP.The WebRTC call is converted into SIP and sent to the SIP server 114,and there it is picked up by the router which instructs the SIP server114 where to route the call to. If the agent is SIP enabled, then thecall goes directly from the SIP server 114 to the agent. If the agent isWebRTC enabled, then the SIP server passes the call back to theWebRTC/call server 110 and the call is sent from there to the agent. Theagents may be reached at one or more agent devices 112 which mayinclude, for example, desktop or portable computers, tablets,smartphones, or any other device capable of running a web browser, or atagent telephones 116. The agent telephones 116 may be, for example, SIPphones for engaging in voice-over-IP (VoIP) communication via, forexample, a SIP server 114.

According to one exemplary embodiment, the contact center also includesa web monitor 140 for monitoring customer's activity on the web server120. In other embodiments, the web monitor 140 may be hosted by theorganization and may be a software module running on the web server 120or on a separate server. Systems and methods for monitoring a customeror web visitor are described in more detail in, for example, in U.S.application Ser. No. 13/293,575 filed in the United States Patent andTrademark Office on Nov. 10, 2011, and titled “SYSTEM FOR INTERACTINGWITH A WEB VISITOR,” the entire disclosure of which is incorporatedherein by reference.

The contact center may also include a database server 150 for storinginformation relating to the customers and their interactions with theorganization and the contact center. Such information may include, forexample, historical data collected by prior agents regarding prior callsand prior issues or requirements, contact information such as names,addresses, and telephone numbers, lists of products owned by thecustomer, and the like.

In some exemplary embodiments, the contact center also includes an OOBapplication server 130 separate from the web server 120 configured toprovide OOB or supplemental communications channels to the customerend-user devices 12. For example, in some embodiments the web server 120is configured to handle and supply functionality related to WebRTC callsbetween the web browser 11 and the WebRTC/call server 110 while the OOBapplication server 130 is configured to provide code and/or mediaassociated with the out-of-band communication channels. In otherembodiments, the out-of-band communication channel functionality may beprovided by the web server 120. These out-of-band communicationschannels may include, without limitation, channels that provide webbrowser-based forms, text chats, video, and other types of media, thatmay typically be presentable by a web server to a customer via a webbrowser. For example, text-based chat may be used for increased accuracywhen communicating addresses, email addresses, and credit card paymentinformation, and to provide URLs to web pages to answer user questions.The OOB channels may also be used for video tutorials, officialdocumentation, and screen sharing for demonstrating usage. OOB channelsmay also provide some redundancies in the case of poor connections inthe real-time communication channel. In this regard, the WebRTC/callserver 110 may assist in establishing socket connections between thecustomer end-user device 12 and the out-of-band application server 130and/or the agent device 112.

According to one exemplary embodiment of the invention, an end userviewing a website provided by the web application 122 (referred to asthe website visitor) may decide to speak to an agent for askingquestions about products viewed on the website, engage in a particulartransaction, or for receiving any other assistance from the agent. Aconventional method for initiating this conversation is by dialing atelephone number (e.g., a toil-free or “1-800” number). The user mayalso request (e.g. via email) that the agent call the customer at aparticular telephone number, or may engage in a text-based chat with theagent via the web browser 11. According to exemplary embodiments of thepresent invention, the end user may, in addition or in lieu of theseconventional contact mechanisms, establish a WebRTC call, with an agentvia the web browser. Using WebRTC allows a user to participate in a realtime voice conversation with an agent, thereby increasing theirengagement, while reducing the costs associated with operating a contactcenter reliant on standard PSTN telephone systems. In addition, WebRTCcalls may be associated with particular browser sessions, therebysimplifying the task of associating OOB channels with the “in-band”audio/video channel.

The various servers 110, 114, 130, 150, 160, and web monitor of FIG. 1may each include one or more processors executing computer programinstructions and interacting with other system components for performingthe various functionalities described herein. The computer programinstructions are stored in a memory implemented using a standard memorydevice, such as, for example, a random access memory (RAM). The computerprogram instructions may also be stored in other non-transitory computerreadable media such as, for example, a CD-ROM, flash drive, or the like.Also, although the functionality of each of the servers is described asbeing provided by the particular server, a person of skill in the artshould recognize that the functionality of various servers may becombined or integrated into a single server, or the functionality of aparticular server may be distributed across one or more other serverswithout departing from the scope of the embodiments of the presentinvention.

FIGS. 2A and 2B are flowcharts of a process for connecting a webapplication user to a contact center agent according to one exemplaryembodiment of the present invention. The process may be described interms of one or more software routines executed, by one or moreprocessors based on computer program instructions stored, in memory. Aperson of skill in the art should recognize, however, that the processmay be executed via hardware, firmware (e.g. via an ASIC), or incombination of software, firmware, and/or hardware. Furthermore, thesequence of steps of the process is not fixed, but may be altered intoany desired sequence as recognized by a person of skill in the art.

The process starts, and in step 200, the web monitor 140 tracks a user'ssession on a web application, such as, for example, the web application122 provided by the web server 120. In this regard, a user invokes thebrowser 11 in the end-user device 12 to access the web application 122.The user may interact with the website/application by navigating thoughthe pages of the website, selecting different links, submittinginformation, initiating transactions, or performing other actions aswill be apparent to a person of skill in the art. The navigating of thevarious pages and the actions performed while visiting the website istracked by the web monitor 140 as discussed in further detail in theabove-referenced U.S. application Ser. No. 13/293,575. For example,while using the web application 122, a session identifier (a “sessionID” or “session token” or, alternatively, login information associatedwith a user account) may be granted and associated with the customerend-user device 12 and/or the web browser running thereon, therebyallowing the web application 122 and other servers operated by theorganization and/or the contact center to identify the user and to trackthe user's activity.

According to one exemplary embodiment, the web monitor 140monitors/tracks the user's activity on the web application 122 todetermine the intent or goals of the user while using the website (e.g.,determining which category of products or services the user isinterested in purchasing or determining the problem that the user wouldlike to resolve) and associate this computed result with the user'ssession identifier. According to one exemplary embodiment, the webmonitor 140 supplies to the routing server 160 information regarding themonitored activity of the user as associated with a particular sessionidentifier.

While perusing the information on the website, the user may decide tospeak to a customer service representative to obtain information or toask for assistance in regards to a product or service being viewed.According to one example, the visitor may transmit the command toinitiate the call by selecting a “call” button. According to oneexemplary embodiment, the web application interprets the command as acommand to initiate a browser based real time communication channel(referred to as a WebRTC call).

In step 202, the WebRTC/call server 110 receives the request to initiatethe WebRTC call with a customer service representative. According to oneexemplary embodiment, the request to initiate the call includes, forexample, a Session Description Protocol (SDP) offer (as described inInternet Engineering Task Force (IETF) Request for Comments (RFC) 3264),which may include an Interactive Connectivity Establishment (ICE)candidate (as described in IETF RFC5245). The offer may includeinformation such as a session identifier for identifying the requestedsession, and an IP address of the requesting end-user device.

In step 203, the WebRTC/call server 110 translates the WebRTC call to aSIP call using a SIP protocol, and sends a request (e.g. via an INVITEmessage) to the SIP server 114. Although a SIP call is used as anexample, a person of skill in the art should recognize that a differentprotocol for VoIP communication may be used instead of SIP, such as, forexample, H.323.

In other embodiments of the present invention, the web server 120 mayprovide the JavaScript that drives WebRTC functionality to the webbrowser. When the user activates a WebRTC session, the other party ismatched to the WebRTC/call server 110. The WebRTC/call server 110 actsas a proxy or gateway for connection to the actual (end-)party of theuser's WebRTC session, where the actual party may be, for example, aWebRTC enabled agent or a SIP enabled agent.

In step 204, the routing server 160 is invoked by the SIP server 114 foridentifying an appropriate agent to route the call.

In step 206, a determination is made by, for example, the SIP server 114in combination with the router, as to whether the identified agent isassociated with a WebRTC capable browser. If the answer is NO, the SIPserver transmits, in step 214, a SIP call to the selected agent. Forexample, the SIP server 114 transmits a SIP INVITE message to theselected agent's SIP device (e.g. telephone 116). The selected agentthus communicates with the website visitor via his or her SIP device,while the website visitor communicates with the selected agent via theweb browser 111. In some exemplary embodiments, this WebRTC call(referred to as an in-band connection) is used solely for voice (e.g.,audio only). In other exemplary embodiments, the connection includesboth audio and video. Referring again to step 206, if a determination ismade that the selected agent has a WebRTC-capable browser, the SIPserver 114 transmits a SIP call for the agent to the WebRTC/call server110. In this regard, the SIP server 114 transmits a SIP INVITE messageincluding an address of the selected agent.

In step 210, the WebRTC/call server 110 converts the SIP call to aWebRTC call. In this regard, the WebRTC/call server 110 acts as abidirectional gateway between WebRTC and SIP based calls.

In step 212, the WebRTC/call server 110 sends the WebRTC call to thebrowser in the selected agent's device 112. Thus, both the agent and thewebsite visitor engage in communication via their respective webbrowsers.

FIG. 3 is a more detailed flow diagram of step 204 of FIG. 2A forselecting an appropriate agent for routing an incoming call according toone exemplary embodiment of the invention. In step 302, the routingserver 160 receives the routing information (e.g., the location of theuser on the web app) from the web monitor 140 to assist in routing thecall to an appropriate customer service representative. In step 304, therouting server 160 attempts to determine the user's intentions (e.g.,purchasing a product technical support, etc.). In step 306, the routingserver 160 determines if the routing information is sufficient todetermine the user's intent. If there is sufficient information, therouting server selects an appropriate agent in step 312, and informationidentifying the selected agent such as, for example, an agentidentifier, telephone number, and/or IP address is sent in step 314 todie WebRTC/call server 110.

Referring again to step 306, if the routing server determines that theinformation received is insufficient for routing the call, additionalrouting information may be collected in step 308 from the websitevisitor. According to one exemplary embodiment, the routing serverinvokes the OOB application server 130 for obtaining the additionalinformation. In one exemplary embodiment of the present invention, theOOB application server 130 displays one or more prompts (e.g., web formsor a series of prompts in a wizard) via an OOB channel to obtain theadditional information. For example, a webpage may be displayed to thewebsite visitor inquiring additional details on the call, such as, forexample, the reason for the call, a particular language that ispreferred, and the like.

According to one exemplary embodiment, the OOB application server 130provides one or more OOB channels of communication within the browser inaddition to (e.g., concurrently with) the real-time communicationchannel (e.g., the WebRTC connection).

According to one exemplary embodiment, the OOB application server 130forwards the additional information to the routing server 160 or to thecall server 114 to route the call to the appropriate customer servicerepresentative.

In embodiments of the present invention which include the web monitor140, the one or more prompts for additional information may be selectedbased on the sufficiency of the information determined by the webmonitor 140. For example, the web monitor 140 may determine that a useris interested in obtaining product support because the user has beenbrowsing troubleshooting pages. However, in some circumstances the webmonitor 140 may not have sufficient information to determine theparticular product that the user is having issues with. As such, whenthe user makes a request to establish a real-time communication channelwith a customer service representative, the out-of-band applicationserver 130 may first prompt the user to indicate that it believes thatthe user is looking for customer support and may ask the user toidentify a product from a list of products that the user would like helpwith.

According to one exemplary embodiment of the invention, the sessionidentifier transmitted with the request for a WebRTC call is used toassociate the website user with the particular session of the webapplication, the user's call request, and the user's responses to theweb-browser based prompts.

The additional routing information may be combined with the previouslycollected routing information and reassessed in step 304 to determine ifthere is sufficient information to determine a user's intentions. Theprocess may be repeated until sufficient information is received. Theuser may also choose to cancel the call request rather than to continueto answer questions via the web prompt, in which ease the call requestis ended in step 310.

FIG. 4 is a flow diagram of a process for establishing an OOB channelconnection between the customer end-user device 12 and the agent device112 according to one exemplary embodiment of the invention. According toone exemplary embodiment, the one or more out-of-band channels may beassociated with the session identifier associated with the correspondingbrowser-based real-time communication channel established as described,for example, with respect to FIGS. 2A and 2B. As discussed above, theout-of-band information may include, but is not limited to, text, chats,screen sharing, shared documents, an inline frame (“iframe”) fordisplaying web pages, and the like.

The out-of-band application server 130 receives request to establish anout-of-band channel in step 402. Either the user or the customer servicerepresentative (CSR) may make this request via their web browsers ontheir end-user devices and the out-of-band channel may be activated atthe contact center. The request may identify one or more types ofout-of-band channels (e.g., text chat, screen sharing, etc.) to beestablished. The out-of-band application server 130 also uses sessionidentifiers to identify 404 the user and the CSR to be connected. Theout-of-band application server 130 then establishes a connection (e.g.,a WebSocket connection) between the user and the CSR using theirrespective session identifiers. This connection can be used to provide achannel for communicating the out-of-band information between the userand the CSR.

As described above, according to one exemplary embodiment of the presentinvention, the out-of-band channels and out-of-band information are usedto supplement the “in-band” WebRTC-based voice and/or videocommunication channel, by providing additional communication channelssuch as text chat, screen sharing, and the like.

In some embodiments of the present invention, the party (e.g., the useror the CSR) not requesting the out-of-band channel may be prompted toconfirm or reject the request to establish the out-of-band channel. Inaddition, in some embodiments of the present invention, separateconnections (e.g., separate WebSocket connections) are establishedbetween the user and the CSR (e.g., the web browsers used by the userand the CSR) for each type of out-of-band channel, or some or all ofthese connections can be shared by the types of out-of-band channelsused.

FIG. 5A is an exemplary screen shot of an exemplary browser window 100displayed on the customer end-user device 12 where a customer using thecustomer end-user device 12 is shopping on the “ACME Products” websiteaccording to one exemplary embodiment of the present invention. Afterperusing the website, the user may want to speak to a customer servicerepresentative to obtain information or to ask for assistance in regardto a product or service being viewed by the user. According to oneexemplary embodiment, the website provides a button 101 to initiate arequest for a WebRTC call with the related contact center to speak withan agent. In other embodiments, the opportunity to establish a call maybe indicated with a pop-up window, an overlay, or another object on theweb page.

In the illustrated example, a request to establish a WebRTC call istransmitted by the browser 111 in response to the user's selection ofthe button 101. The established WebRTC call between the website visitorand an agent may be audio only, or audio and video. FIG. 3B is anexemplary screen shot of a browser window 100 with a pop-up window 102displaying a real-time video call with an agent.

FIGS. 6A and 6B are exemplary screen shots of pop-up windows 103, 105displayed for requesting additional information from the website visitoraccording to one exemplary embodiment of the invention. The pop-upwindows may be used to prompt the user to select from a choice oflanguages, to indicate whether the call relates to sales, support, orother customer service, and/or to identify a category of products towhich the call relates.

FIG. 7 is an exemplary screen shot of a browser window 100 displayed bythe end-user device 1.2 of a customer engaged in a communication sessionwith a customer service representative and with a plurality ofout-of-band channels according to one exemplary embodiment of thepresent invention. In the example of FIG. 7, a user's browser window mayinclude a plurality of sub-windows 102-108, where these sub-windowsprovide additional out-of-band information and communications channelsincluding, without limitation, a video chat window 102, a text chatwindow 104, a document viewer window 106, and a video window 108.Embodiments of the present invention are not limited to the listedwindows and may include other windows for displaying other types ofcontent such as, for example, a digital “whiteboard” for drawingdiagrams, displaying images, displaying billing information, anddisplaying a live view of a customer service representative's computerscreen, or a portion thereof, for demonstrating the use of a product orservice, or the like. In addition, as shown in the example of FIG. 5B,in some embodiments of the present invention, a sub-window 102 a mayfloat in a separate browser window.

While the present invention has been described in connection withcertain exemplary embodiments, it is to be understood that the inventionis not limited to the disclosed embodiments, but, on the contrary, isintended to cover various modifications and equivalent arrangementsincluded within the spirit and scope of the appended claims, andequivalents thereof. For example, in some embodiments of the presentinvention may provide multi-party calls involving, for example, multipleagents interacting with a customer over WebRTC and the OOB communicationchannels, call transfer between agents, supervisor silent monitoring orwhisper coaching (e.g., supervisor speaking to the agent without thecustomers being able to listen in) are also available and end users orcustomers may be able to conference in other parties via WebRTC.

While embodiments of the present invention illustrate a call server androuting calls via the call server, in some embodiments of the presentinvention, customer service representatives communicate with usersdirectly via WebRTC connections without an intervening call server. Inother embodiments a SIP server is included in the loop for purposes ofcall control, such as transfer, conferencing, or supervisors silentmonitoring and whisper coaching.

In addition, while embodiments of the present invention have beendescribed above in the context of WebRTC, other embodiments of thepresent invention may use other web-browser based conferencingtechnologies such as CU-RTC-WEB that similarly do not depend on theinstallation of additional plugins such as Adobe® Flash® or the Google®Talk plugin.

What is claimed is:
 1. A method for connecting a website user to acontact center agent, the method comprising: monitoring an interactionbetween a website and a web browser running on a computing deviceoperated by the website user; receiving, by the processor, a callrequest from the web browser via the website; identifying an agent or aninteractive voice response based on the monitored user interaction; andestablishing a communication channel, supported by the web browser,between the website user and the identified agent or the interactivevoice response, wherein the web browser is configured to: control amicrophone of the computing device, and transmit audio captured by themicrophone via the communication channel.
 2. The method of claim 1,wherein the monitored user interaction is associated with a sessionidentifier.
 3. The method of claim 2, wherein the establishing thecommunication channel comprises identifying a user session using thesession identifier.
 4. The method of claim 1, wherein the communicationchannel comprises a WebRTC call leg.
 5. The method of claim 1, whereinthe communication channel comprises a SIP call leg between the agent andthe user.
 6. The method of claim 1, wherein the communication channelcomprises a PSTN call leg between the agent and the user.
 7. The methodof claim 1, wherein the communication channel comprises a WebRTC callleg between the agent and the user.
 8. The method of claim 1, whereinthe communication channel comprises an audio channel, and wherein theaudio is transmitted in the audio channel.
 9. The method of claim 1,wherein the communication channel comprises a video channel.
 10. Asystem for providing connections with a contact center, the systemcomprising: a WebRTC-SIP gateway configured to receive a plurality ofrequests for connections between a web browser corresponding to asession of a user on a website and the contact center; a routing serverconfigured to route the requests for connections to a plurality ofcustomer service representatives of the contact center; and a callserver for establishing a communication channel via the WebRTC-SIPgateway between the web browser of the user and a customer servicerepresentative of the contact center, wherein the WebRTC-SIP gateway isconfigured to establish a WebRTC connection with the web browser, theweb browser running on a computing device of the user and the webbrowser controlling a microphone of the computing device.
 11. The systemof claim 10, wherein the routing server is configured to route a requestto a customer service representative of the customer servicesrepresentatives via the call server.
 12. The system of claim 10, whereinthe user on the website is associated with a session identifier.
 13. Thesystem of claim 12, further comprising a monitoring server configured tomonitor user interaction associated with the user of the website,wherein the routing server is configured to route the request to acustomer service representative in accordance with the monitored userinteraction, and wherein the call server is configured to establish thecall by identifying the user using the session identifier.
 14. Thesystem of claim 10, wherein the call server comprises a SIP server. 15.The system of claim 10, wherein the WebRTC-SIP gateway is furtherconfigured to establish a WebRTC-to-SIP connection.
 16. The system ofclaim 10, wherein the WebRTC-SIP gateway is further configured toestablish a WebRTC-to-WebRTC connection.
 17. The system of claim 10,wherein the WebRTC-SIP gateway is further configured to establish aSIP-to-SIP connection.
 18. The system of claim 10, wherein the callscomprise an audio channel.
 19. The system of claim 10, wherein the callscomprise a video channel.